fix(helm): always create default metrics source if traces are enabled #2182
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After introducing: #1647 we got into a bit of a situation for users who enable traces but don't enable metrics.
The problem's root cause is that traces pipeline now requires default metrics endpoint to be available
sumologic-kubernetes-collection/deploy/helm/sumologic/values.yaml
Line 3498 in 9bf45ca
This PR addresses that by always creating default metrics endpoint when traces are enabled in the chart.
There's a separate issue that tries to address the meaning of different configuration options in
values.yaml
that's tracked in #2183.